Enterprise femtocell signaling

ABSTRACT

A mobile device sends a request for a unique wireless network session identifier and receives, based on the request, the unique wireless network session identifier. The mobile device determines whether the unique wireless network session identifier includes a femtocell identifier. The mobile device applies one set of configuration settings when the unique wireless network session identifier includes the femtocell identifier, and applies a different set of configuration settings when the unique wireless network session identifier does not include the femtocell identifier.

BACKGROUND

In wireless data networks, the physical network may include traditionalwireless communication stations (macro cell base stations) installed atfixed locations and used to communicate with the wireless accessterminals. Another type of base station, called a femtocell, may also beused in such networks. A femtocell may be a small form factor wirelessbase station, typically designed for use in a home or small business.The femtocell may connect to a service provider's network via broadband(such as DSL or cable). The femtocell may allow service providers toextend service coverage indoors, especially where access would otherwisebe limited or unavailable. Currently, there is no mechanism tospecifically distinguish, to the access terminal, data services providedthrough a femtocell and data services provided through a macro cell basestation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example network in which systems and/ormethods described herein may be implemented;

FIG. 2 is a diagram of example components of a base station, afemtocell, a data server, or an account server of FIG. 1;

FIG. 3 is a diagram of example components of a mobile device depicted inFIG. 1;

FIG. 4 is a diagram of example functional components of a femtocelldepicted in FIG. 1;

FIG. 5 is a diagram of an example format for a unicast access terminalidentifier (UATI) according to an implementation described herein;

FIG. 6 is a diagram of example functional components of a mobile devicedepicted in FIG. 1;

FIG. 7 is an example of a user interface including a femtocell useindicator icon;

FIG. 8 is an example of another user interface including a notice ofdata usage;

FIG. 9 is an example configuration menu for managing data transfers;

FIG. 10 is a diagram of example functional components of account serverdepicted in FIG. 1;

FIGS. 11-13 are a flow charts of an example process for managing mobiledevice behavior based on a femtocell indication according to animplementation described herein; and

FIG. 14 is a flow chart of an example process for providing femtocelluse identification according to an implementation described herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

Systems and/or methods described herein may distinguish, for a mobiledevice, data services provided through a femtocell and data servicesprovided through a macro cell base station. Mobile devices may receive afemtocell use indicator included within a unicast access terminalidentifier (UATI), or another unique wireless network sessionidentifier, that can enable femtocell-specific behavior. In oneimplementation, the mobile device may use the femtocell indication todisplay a visual icon to announce that the mobile device is connected toa femtocell, and not a macro cell. In another implementation, the mobiledevice may use the femtocell indication to offer options for serviceand/or usage behavior (e.g., differentiated pricing) based on whetherthe network coverage is provided by a femtocell or a macro cell.

As used herein, the terms “subscriber” and/or “user” may be usedinterchangeably. Also, the terms “subscriber” and/or “user” are intendedto be broadly interpreted to include a mobile device or a user of amobile device.

FIG. 1 is a diagram of an example network 100 in which systems and/ormethods described herein may be implemented. Network 100 may generallyillustrate a wireless communication system based on the Evolution-DataOptimized (EVDO) mobile communication standard. In alternativeimplementations, other communication standards could be used.

As illustrated, network 100 may include multiple mobile devices 110-1,110-2, . . . , 110-N (referred to herein collectively as “mobile devices110” or generically as “mobile device 110”); a wireless core network120, including a packet control function (PCF 125); a base station 130;a femtocell 140; a data server 150; and an account server 160.Components of network 100 may interconnect via wired and/or wirelessconnections. Three mobile devices 110, one wireless core network 120,one PCF 125, one base station 130, one femtocell 140, one data server150, and one account server 160 have been illustrated in FIG. 1 forsimplicity. In practice, there may be more mobile devices 110, networks120, PCFs 125, base stations 130, femtocells 140, data servers 150,and/or account servers 160.

Mobile device 110 may include a device capable of transmitting andreceiving data (e.g., voice, text, images, and/or multimedia data) overwireless core network 120. For example, mobile device 110 may be aself-contained data device, such as a mobile telephone, a smart phone,an electronic notepad, a personal digital assistant (PDA), etc. Inanother implementation, mobile device 110 may be connected to acomputing device, such as laptop or personal computer. Mobile devices110 may establish wireless communication sessions with base stations 130or femtocells 140 using identical protocols. The wireless communicationsessions may be used for voice (e.g., telephone calls) or data sessions.

Wireless core network 120 may include components to implement the corenetwork of the EVDO standard. One implementation of such a core networkincludes the Evolved Packet Core (EPC) architecture. In otherimplementations, other network technologies, such as other InternationalMobile Telecommunications-2000 (“3G”), or second-generation wirelesstelephone technology (“2G”), may be implemented instead of or inaddition to EVDO. Components within wireless core network 120 maygenerally be connected over wired or wireless IP-based connections.

PCF 125 may include an entity that manages the relay of packets betweeneither base station 130 or femtocell 140 and another node within network120, such as a packet data serving node (PDSN). Network 120 may includemultiple PCFs 125. In one implementation, PCF 125 may assign, to mobiledevice 110, a UATI that is sent, via either base station 130 orfemtocell 140, to mobile device 110. In an implementation, one PCF 125can support multiple base stations 130 or femtocells 140. In anotherimplementation, a separate PCF 125 may be used for each base station 130and/or femtocell 140.

Base station 130 may represent a base station designed to providewireless communication service (e.g., an access network) to a relativelylarge area and simultaneously serve a relatively large number of mobiledevices 110. Base station 130 may also be referred to herein as a “macrocell” or a “macro cell base station.”

Femtocell 140 may include a device designed to be placed within aresidence or small business setting and may connect to wireless corenetwork 120 via a wired broadband connection. Femtocell 140 may act as abase station for a limited set of active mobile devices, such as up tofour simultaneous mobile devices. In some instances, femtocell 140 maybe self-installed by end-users in the residences or business of theend-users. In an implementation described herein, femtocell 140 mayestablish wireless communication sessions using the same protocols asthat of base station 130, but also providing a femtocell identifier thatmay be detected by mobile device 110.

Although mobile devices 110-2 through 110-N are shown in FIG. 1 asconnecting to base station 130 and mobile device 110-1 is shown asconnecting to femtocell 140, mobile devices 110 may generally connect toeither base station 130 or femtocell 140 (e.g., depending on thelocation of each mobile device 110). In a typical implementation, mobiledevice 110 may connect to femtocell 140 when mobile device 110 is withinrange of femtocell 140. When mobile device 110 moves out of range offemtocell 140, mobile device 110 may switch the connection to basestation 130, where the switch is ideally performed without interruptingthe communication session of mobile device 110.

Data server 150 may include one or more server devices, or other typesof computation or communication devices, that gather, process, search,and/or provide information in a manner described herein. In oneimplementation, data server 150 may include a computer system, a serverdevice, a cable head-end, and/or a broadcasting device capable ofproviding data (e.g., video content, applications, file downloads,advertising, instructions, images, voice content (e.g., voice over IP(VoIP)), application data, and/or other information) to mobile device110.

Account server 160 may include one or more server devices, or othertypes of computation or communication devices, that gather, process,search, and/or provide information in a manner described herein. In oneimplementation, account server 160 may receive and store accountinformation associated with mobile devices 110. Account information mayinclude, for example, pricing plan information that differentiatesbetween femtocell usage and macro cell usage. In one implementation,some of the account information may be provided (e.g., via base station130 or femtocell 140) to mobile device 110 to enable mobile device 110to identify differences in pricing for femtocell usage and macro cellusage. Account server 160 may also monitor data transfers to/from mobiledevice 110 and differentiate between data transfers provided to/frommobile device 110 via a femtocell (e.g., femtocell 140) and datatransfers provided to/from mobile device 110 via a macro cell basestation (e.g., base station 130).

In an implementation described herein, mobile device 110 may includecapabilities to interpret femtocell indicators received from femtocell140. Components of network 100 may differentiate between networkservices provided via macro cell 130 and network services provided viafemtocell 140. In one implementation, mobile device 110 may provideindications (e.g., visual and/or audible indications), to a user, todistinguish femtocell-based services from macro-cell based services. Inanother implementation, mobile device 110 may implement behaviors toshift data usage patterns to prefer one access network (e.g., femtocell140) over another access network (e.g., base station 130).

Although FIG. 1 shows example components of network 100, in otherimplementations, network 100 may include fewer components, differentcomponents, differently arranged components, and/or additionalcomponents than those depicted in FIG. 1. Alternatively, oradditionally, one or more components of network 100 may perform one ormore other tasks described as being performed by one or more othercomponents of network 100.

FIG. 2 is a diagram of example components of a device 200 that maycorrespond to one or more of PCF 125, base station 130, femtocell 140,data server 150, or account server 160. Each of PCF 125, base station130, femtocell 140, data server 150, and account server 160 may includeone or more device 200. As illustrated, device 200 may include a bus210, a processing unit 220, a memory 230, an input device 240, an outputdevice 250, and a communication interface 260.

Bus 210 may permit communication among the components of device 200.Processing unit 220 may include one or more processors ormicroprocessors that interpret and execute instructions. In otherimplementations, processing unit 220 may be implemented as or includeone or more application specific integrated circuits (ASICs), fieldprogrammable gate arrays (FPGAs), or the like.

Memory 230 may include a random access memory (RAM) or another type ofdynamic storage device that stores information and instructions forexecution by processing unit 220, a read only memory (ROM) or anothertype of static storage device that stores static information andinstructions for the processing unit 220, and/or some other type ofmagnetic or optical recording medium and its corresponding drive forstoring information and/or instructions.

Input device 240 may include a device that permits an operator to inputinformation to device 200, such as a keyboard, a keypad, a mouse, a pen,a microphone, one or more biometric mechanisms, or the like. Outputdevice 250 may include a device that outputs information to theoperator, such as a display, a speaker, etc.

Communication interface 260 may include any transceiver-like mechanismthat enables device 200 to communicate with other devices and/orsystems. For example, communication interface 360 may include mechanismsfor communicating with other devices, such as other devices of network100.

As described herein, device 200 may perform certain operations inresponse to processing unit 220 executing software instructionscontained in a computer-readable medium, such as memory 230. Acomputer-readable medium may be defined as a physical or logical memorydevice. A logical memory device may include memory space within a singlephysical memory device or spread across multiple physical memorydevices. The software instructions may be read into memory 230 fromanother computer-readable medium or from another device viacommunication interface 260. The software instructions contained inmemory 230 may cause processing unit 220 to perform processes describedherein. Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes describedherein. Thus, implementations described herein are not limited to anyspecific combination of hardware circuitry and software.

Although FIG. 2 shows example components of device 200, in otherimplementations, device 200 may include fewer components, differentcomponents, differently arranged components, or additional componentsthan depicted in FIG. 2. Alternatively, or additionally, one or morecomponents of device 200 may perform one or more other tasks describedas being performed by one or more other components of device 200.

FIG. 3 is a diagram of example components of mobile device 110. Asillustrated, mobile device 110 may include a processing unit 300, amemory 310, a user interface 320, a communication interface 330, and/oran antenna assembly 340.

Processing unit 300 may include one or more processors, microprocessors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), or the like. Processing unit 300 may controloperation of mobile device 110 and its components. In oneimplementation, processing unit 300 may control operation of componentsof mobile device 110 in a manner described herein.

Memory 310 may include a random access memory (RAM), a read-only memory(ROM), and/or another type of memory to store data and instructions thatmay be used by processing unit 300.

User interface 320 may include mechanisms for inputting information tomobile device 110 and/or for outputting information from mobile device110. Examples of input and output mechanisms might include buttons(e.g., control buttons, keys of a keypad, a joystick, etc.) or a touchscreen interface to permit data and control commands to be input intomobile device 110; a speaker to receive electrical signals and outputaudio signals; a microphone to receive audio signals and outputelectrical signals; and/or a display to output visual information (e.g.,text input into mobile device 110).

Communication interface 330 may include, for example, a transmitter thatmay convert baseband signals from processing unit 300 to radio frequency(RF) signals and/or a receiver that may convert RF signals to basebandsignals. Alternatively, communication interface 330 may include atransceiver to perform functions of both a transmitter and a receiver.Communication interface 330 may connect to antenna assembly 340 fortransmission and/or reception of the RF signals.

Antenna assembly 340 may include one or more antennas to transmit and/orreceive RF signals over the air. Antenna assembly 340 may, for example,receive RF signals from communication interface 330 and transmit themover the air, and receive RF signals over the air and provide them tocommunication interface 330. In one implementation, for example,communication interface 330 may communicate, via antenna assembly 340,with a network and/or devices connected to a network (e.g., network120).

As will be described in detail below, mobile device 110 may performcertain operations in response to processing unit 300 executing softwareinstructions of an application contained in a computer-readable medium,such as memory 310. The software instructions may be read into memory310 from another computer-readable medium or from another device viacommunication interface 330. The software instructions contained inmemory 310 may cause processing unit 300 to perform processes that willbe described later. Alternatively, hardwired circuitry may be used inplace of or in combination with software instructions to implementprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

Although FIG. 3 shows example components of mobile device 110, in otherimplementations, mobile device 110 may contain fewer, different,differently arranged, or additional components than depicted in FIG. 3.In still other implementations, one or more components of mobile device110 may perform one or more other tasks described as being performed byone or more other components of mobile device 110.

FIG. 4 is a diagram of an example functional component of PCF 125. Inone implementation, the functions described in connection with FIG. 4may be performed by one or more components of device 200 (FIG. 2). Asshown in FIG. 4, PCF 125 may include a UATI generator 410.

UATI generator 410 may include hardware or a combination of hardware andsoftware to assign a UATI that includes a femtocell identifier. In a 3Gtelecommunications network, such as an Evolution-Data Optimized (EVDO)network, each mobile device 110 (or access terminal) may be assigned aUATI. The UATI is a universally unique 128-bit address used to addressmobile device 110 when a base station (e.g., base station 130 orfemtocell 140) sends messages to mobile device 110. Whenever mobiledevice 110 crosses a subnet (e.g., the footprint of an access networkdefined by the range of a base station or femtocell), mobile device 110may send a UATI request message that may be received by thecorresponding base station and forwarded to PCF 125. Whileimplementations described herein are primarily described in the contextof a UATI, in other implementations, another unique wireless networksession identifier may be used.

In response to the UATI request, UATI generator 410 may assign a uniqueUATI that includes a femtocell identifier. In one implementation, thefemtocell identifier may be a two-bit value common to all femtocellidentifiers with a service provider's network. The femtocell identifiermay be included within a particular location of the UATI so that mobiledevice 110 may detect the femtocell identifier and, for example, notifya user that mobile device 110 is connected to a femtocell (e.g., incontrast to a macro cell).

Although FIG. 4 shows an example functional component of PCF 125, inother implementations, PCF 125 may include different functionalcomponents, differently arranged functional components, and/oradditional functional components than depicted in FIG. 4.

FIG. 5 depicts an example UATI format 500 according to an implementationdescribed herein. UATI format 500 may include a most significant bits(MSB) section 510 and a least significant bits (LSB) section 520. Afemtocell identifier section 530 may be included, for example, withinMSB section 510.

MSB section 510 may include “n” most significant bits (MSBs) thatrepresent the identifier for a subnet. In one implementation, MSBsection 510 may include 104 bits (e.g., bit numbers 0-103). Leastsignificant bits (LSB) section 520 may include the remaining “128-n”bits that identify a particular sector/device within a subnet. Forexample, LSB section 520 may include 24 bits (e.g., bit numbers104-127).

Femtocell identifier (ID) section 530 may be a particular number andlocation of bits designated for identifying femtocell use. In oneimplementation, femtocell ID section 530 may include bits 48 and 49 asdedicated femtocell indicator bits. For example, all femtocells may usethe same predefined two-bit pattern (e.g., “01”) in femtocell ID section530 to uniquely identify themselves as femtocells. Thus, a UATI providedto mobile device 110 from femtocell 140 may include the predefinedtwo-bit pattern in femtocell ID section 530. Conversely, a UATI providedto mobile device 110 from base station 130 may include a different bitor set of bits in femtocell ID section 530.

Although FIG. 5 shows an example UATI format 500, in otherimplementations, UATI format 500 may include fewer sections, differentsections, differently arranged sections, and/or additional sections thandepicted in FIG. 5.

FIG. 6 is a diagram of example functional components of mobile device110. In one implementation, the functions described in connection withFIG. 6 may be performed by one or more components of device 300 (FIG.3). As shown in FIG. 6, mobile device 110 may include a femtocellindicator module 610 and an application interface module 620.

Femtocell indicator module 610 may include hardware or a combination ofhardware and software that may enable mobile device 110 to recognize afemtocell identifier and to provide an indication to a user. In oneimplementation, when mobile device 110 registers with a femtocell,femtocell indicator module 610 may receive, from femtocell 140, a UATIthat includes a particular femtocell identifier (e.g., a two-bitidentifier in femtocell identifier section 530). Femtocell indicatormodule 610 may parse the UATI to detect the femtocell identifier(included, for example, at bits 48 and 49 of the UATI).

Based on the detection or absence of the femtocell identifier, mobiledevice 110 may apply settings for specific behaviors (e.g.,femtocell-specific behavior or macro cell-specific behavior). Mobiledevice 110 behaviors may include, for example, informing a user ofmobile device 110 of a femtocell connection or a macro cell connection,notifying the user of pricing plan changes based on a femtocell or macrocell connection, and/or managing particular data transfers based on thefemtocell or macro cell connection. In one implementation, for example,femtocell indicator module 610 may initiate display of a femtocellindicator icon for presentation to user whenever mobile device 110 isconnected to a femtocell. An example of a user interface including afemtocell indicator icon is shown in FIG. 7.

As shown in FIG. 7, mobile device 110 may include a display 700 thatincludes a user interface 710. User interface 710 may present statusinformation regarding mobile device 110, such as signal strength,battery life, date/time, and/or network connectivity. In animplementation described herein, user interface 710 may include afemtocell indicator 720. Femtocell indicator 720 may be presented (e.g.,by femtocell indicator module 610) in the form of a distinct visualicon. In one implementation, femtocell indicator 720 may simply providenotice to a user that current network coverage for mobile device 110 isprovided by a femtocell. Thus, in the event a network service provideroffers different service/pricing options for femtocell use and macrocell use, a user of mobile device 110 may be able to make an informeddecision selecting available services.

For example, assume a user has a subscription plan with a networkservice provider that is designed to promote femtocell use. Assume thesubscription plan includes a per megabyte (MB) charge for data transferusing a macro base station (e.g., base station 130) and no charge (e.g.,unlimited transfers) for data transfer using a femtocell (e.g.,femtocell 140). Femtocell indicator 720 may provide information to auser of mobile device 110 to enable the user to make informed choicesbetween the available subscription plan services.

Returning to FIG. 6, femtocell indicator module 610 may continue todisplay the femtocell indicator icon as long as mobile device 110remains associated with femtocell 140. When mobile device 110 moves outof range of femtocell 140, indicator module 610 may receive a new UATIthat may include another femtocell identifier (e.g., the same two-bitfemtocell identifier, associated with another femtocell) or no femtocellidentifier (e.g., indicating the UATI is from a macro base station). Ifa femtocell identifier is included in the new UATI, femtocell indicatormodule 610 may, for example, continue to present the femtocell indicatoricon. If no femtocell identifier is included in the new UATI, femtocellindicator module 610 may remove the femtocell indicator icon from thedisplay.

Application interface module 620 may include hardware or a combinationof hardware and software that may enable mobile device 110 to recognizea femtocell identifier and to control communications to/from mobiledevice 110 based on the femtocell identifier. In one implementation,application interface module 620 may identify a call for a data sessionthat is initiated by mobile device 110 (e.g., by a particularapplication running on mobile device 110) and apply specific behaviorfor the data session based on the presence (or absence) of the femtocellidentifier. In an example implementation, application interface module620 may be included as part of an operating systems (OS) and provide aTCP/IP stack to manage communication applications.

In an implementation, application interface module 620 may retrieve(e.g., from account server 160) and/or store information about a user'sdata subscription plan and/or subscription profile. For example, theaccount data may include information about a subscriber's billing planfor data (e.g., per MB fees, pre-paid MB limits, unlimited access,etc.). In one implementation, the subscriber's billing plan may include,for example, shared data limits among multiple devices (e.g., a “familyplan”). Updates to a subscriber's account data may be requested bymobile device 110 during a session initiation exchange. Additionally, oralternatively, updates to a subscriber's account data may be initiatedby, for example, account server 160, when a subscriber's billing plan ischanged.

Application interface module 620 may provide pricing notifications foractivity with different access networks. For example, if the user'ssubscription plan includes distinctions between data transfers using afemtocell (e.g., femtocell 140) versus a base station (e.g., basestation 130), application interface module 620 may provide a generalnotification, to the user, of data transfer costs based on the currentaccess network. The general notification may include, for example, anindication, when the UATI is received, that macro cell or femtocellpricing may be applied. In another implementation, the generalnotification may include actual data rates (e.g., a per MB rate)associated with the current access network. Pricing plan information maybe obtained, for example, from account server 160 in advance and storedin a memory of mobile device 110.

Application interface module 620 may also track data usage forparticular data session. In one implementation, application interfacemodule 620 may monitor data transfers that may be initiated by anapplication running on mobile device 110. For example, applicationinterface module 620 may identify when an application requests a datatransfer using a service with pre-paid data transfer limits and/or perMB fees. In one implementation, application interface module 620 maynotify a user of mobile device 110 that an application is consumingresources of a limited data service (e.g., per MB fees, pre-paid MBlimits, etc.) associated with an access network for base station 130.Similarly, application interface module 620 may notify a user of mobiledevice 110 that an application is consuming resources under a particularbilling rate (e.g., per MB fees, pre-paid MB limits, etc.) associatedwith an access network for femtocell 140. Conversely, applicationinterface module 620 may provide no notice to the user of mobile device110 if the application is consuming resources of an unlimited dataservice associated with an access network (e.g., for femtocell 140).

FIG. 8 includes an example of another user interface including a noticeof data usage. As shown in FIG. 8, mobile device 110 may include display700 that includes a user interface 810. User interface 810 may includestatus information similar to that described in connection with userinterface 710 above, with the exception that user interface 810 may notinclude a femtocell indicator 720. User interface 810 may also include anotice 820 to inform a user of mobile device 110 that an application isattempting to consume resources of a limited data service. Notice 820may include, for example, information that is specific to a subscriber'saccount, such as the per MB cost, the amount of pre-paid MBs (e.g.,total per month or currently remaining), etc.

As shown in FIG. 8, notice 820 may include a name of an applicationassociated with a data request and the general charges associated withthe request (e.g., “‘Time Tracker’ is requesting a data transfer. Youraccount will be charged $1.99 per MB.”). In another implementation,notice 820 may include more generic information, such as simplyindicating that a data transfer using a macro base station has beenrequested, stating that there may be a fee for the pending datatransfer, etc. In one implementation, notice 820 may also includecontrol buttons 830 to allow a user to permit (e.g., “continue”) or stop(e.g., “cancel”) a data transfer.

Returning to FIG. 6, application interface module 620 may also includeuser configurable setting to instruct mobile device 110 how to managedata transfers for particular applications when using a femtocell (e.g.,femtocell 140) versus a macro cell base station (e.g., base station130). For example, application interface module 620 may presentconfigurable settings for encouraging lower cost data transfers (e.g.,when mobile device 110 is connected to a femtocell) for non-criticalapplications, while restricting and/or notifying users of higher costdata transfers (e.g., when mobile device 110 is connected to a macrocell base station). In one implementation, configuration settings mayinclude default settings that may be adjusted by a user. In anotherimplementation, the configuration settings may vary based on pricingplan information received, for example, from account server 160. FIG. 9provides a sample configuration menu for managing data transfers.

As shown in FIG. 9, mobile device 110 may include display 700 thatincludes a user interface 910. User interface 910 may include statusinformation similar to that described in connection with user interfaces710 and/or 810 above. User interface 910 may also include aconfiguration menu 920 to enable a user of mobile device 110 to managedata transfer settings for particular applications. In oneimplementation, configuration menu 920 may include a list ofapplications (or programs) residing on mobile device 110 (e.g., “App.1,” “App. 2,” “App. 3,” etc.). Additionally, or alternatively,configuration menu 920 may include groups of applications (e.g., “AllApps”) and/or sub-groups of applications residing on mobile device 110.

In an example implementation, for each application or application group,configuration menu 920 may include configurable settings for managingdata transfers when mobile device 110 is not connected to a femtocell.Settings may include, example, allowing data transfers for non-femtocellconnections (e.g., “Yes”), disabling data transfers for non-femtocellconnections (e.g., “No”), or notifying when a data transfer is requestedvia non-femtocell connections (e.g., “Ask”). In one implementation,configuration menu 920 may also include control buttons 930 to allow auser to return to a set of default configurations (e.g., “reset”) oraccept user selections (e.g., “OK”).

While options in configuration menu 920 are presented in the context ofparticular applications or groups of applications, in otherimplementations configuration menu 920 may include different settingand/or categories. For example, configuration menu 920 may distinguishbetween data transfers initiated by a user and data transfersautomatically initiated by an application. Configuration menu 920 isstructured based on the presumption that services provided by a serviceprovider may provide advantageous price plans for femtocell use overmacro cell use. However, other configuration menus and options may beused.

FIGS. 6-9 show example functional components and user interfaces ofmobile device 110. In other implementations, mobile device 110 mayinclude fewer functional components, different functional components,differently arranged functional components, and/or additional functionalcomponents than depicted in FIG. 6. Alternatively, or additionally, oneor more functional components of mobile device 110 may perform one ormore other tasks described as being performed by one or more otherfunctional components of mobile device 110. Furthermore, the exampleuser interfaces presented in connection with FIGS. 7-9 may includedifferent and/or differently arranged information.

FIG. 10 is a diagram of example functional components of account server160. In one implementation, the functions described in connection withFIG. 10 may be performed by one or more components of device 200 (FIG.2). As shown in FIG. 10, account server 160 may include stored useraccounts 1010 and a data transfer monitor 1020.

Stored user accounts 1010 may include account information associatedwith mobile device 110. For example, stored user accounts 1010 mayinclude subscription information associated with each mobile device 110.Subscription information may include, for example, a level ofsubscription service (e.g., per MB fees, pre-paid MB limits, unlimitedaccess, etc.) associated with the user account, femtocell and/ortime-based pricing plans, order histories, user preferences, etc. In oneimplementation, select information from stored user accounts 1010 may beprovided to mobile device 110 (e.g., application interface module 620)for use in controlling communications to/from mobile device 110 based onfemtocell connectivity.

Data transfer monitor 1020 may include hardware or a combination ofhardware and software to allow account server 160 to monitor datatransfers to/from mobile device 110. In one implementation, datatransfer monitor 1020 may differentiate between data transfers providedto/from mobile device 110 via a femtocell (e.g., femtocell 140) and datatransfers provided to/from mobile device 110 via a macro cell basestation (base station 130). Account server 160 may associate themonitored data transfer information with a user account (e.g., for theuser of mobile device 110), store the data transfer information, and/orprovide the data transfer information to a billing system (not shown).In one implementation, data transfers provided to/from mobile device 110via a femtocell (e.g., femtocell 140) may be billed at a different ratethan data transfers provided to/from mobile device 110 via a macro cellbase station (base station 130). In another implementation, femtocelluse may be incentivized by other plan structures, such as rewardsprograms, rebates, etc. based on femtocell use.

Although FIG. 10 shows example functional components of account server160, in other implementations, account server 160 may include fewerfunctional components, different functional components, differentlyarranged functional components, and/or additional functional componentsthan depicted in FIG. 10. Alternatively, or additionally, one or morefunctional components of account server 160 may perform one or moreother tasks described as being performed by one or more other functionalcomponents of account server 160.

FIGS. 11-13 are flow charts of an example process 1100 for managingmobile device behavior based on a femtocell indication according to animplementation described herein. Process 1100 may be performed by mobiledevice 110. In another implementation, some or all of process 1100 maybe performed by mobile device 110 in conjunction with, for example,account server 160.

Process 1100 may include receiving configuration settings for femtocelland/or macro cell use (block 1110). For example, as described above inconnection with FIG. 6, application interface module 620 may includeuser configurable setting to instruct mobile device 110 how to managedata transfers for particular applications when using a femtocell (e.g.,femtocell 140) versus a macro cell base station (e.g., base station130). For example, application interface module 620 may presentconfigurable settings for encouraging lower cost data transfers (e.g.,when mobile device 110 is connected to a femtocell) for non-criticalapplications, while restricting and/or notifying users of higher costdata transfers (e.g., when mobile device 110 is connected to a macrocell base station). The configurable settings may vary based on pricingplan information received, for example, from account server 160.

Process 1100 may include requesting and receiving a UATI (block 1120),parsing the UATI for a femtocell identifier (block 1130), anddetermining if a femtocell identifier is present in the UATI (block1140). For example, as described above in connection with FIG. 6, whenmobile device 110 registers with a femtocell, femtocell indicator module610 may receive, from femtocell 140, a UATI that includes a particularfemtocell identifier (e.g., a two-bit identifier in femtocell identifiersection 530). Femtocell indicator module 610 may parse the UATI todetect the femtocell identifier (included, for example, at bits 48 and49 of the UATI).

If a femtocell identifier is detected (block 1140—YES), process 1100 mayinclude applying settings for femtocell specific behavior (block 1150).For example, as described above in connection with FIG. 6, based onrecognition of the femtocell identifier, mobile device 110 may applysettings for femtocell-specific behavior. Femtocell-specific behaviormay include, for example, informing a user of mobile device 110 of afemtocell connection, notifying the user of pricing changes based on thechange from a macro cell connection to a femtocell connection, and/ormanaging particular data transfers based on the femtocell connection.

If a femtocell identifier is not detected (block 1140—NO), process 1100may include applying settings for macro cell-specific behavior (block1160). For example, when mobile device 110 receives a UATI without afemtocell identifier, mobile device 110 may apply settings for macrocell-specific behavior. Macro cell-specific behavior may include, forexample, removing a femtocell indicator (e.g., if mobile device 110 waspreviously connected to a femtocell), notifying the user of pricingchanges based on the change from a femtocell connection to a macro cellconnection, and/or managing particular data transfers based on the macrocell connection.

Process block 1150 may include the process blocks depicted in FIG. 12.As shown in FIG. 12, process block 1150 may include presenting, on adisplay, a femtocell use indicator (block 1210), providing a generalnotification of data transfer costs based on the femtocell use (block1220), and/or providing a per-session notification of data transfercosts based on the femtocell use (block 1230). For example, femtocellindicator module 610 may initiate display of a femtocell indicator icon(e.g., femtocell indicator 720) for presentation to a user whenevermobile device 110 is connected to a femtocell. If the user'ssubscription plan includes distinctions between data transfers using afemtocell (e.g., femtocell 140) versus a macro cell base station (e.g.,base station 130), application interface module 620 may provide ageneral notification, to the user, of data transfer costs based on thefemtocell connection. Application interface module 620 may also trackdata usage for particular data session, such as data transfers that maybe initiated by an application running on mobile device 110. Applicationinterface module 620 may notify a user of mobile device 110 that anapplication is consuming resources of a limited data service (e.g., perMB fees, pre-paid MB limits, etc.) associated with, for example, anaccess network for femtocell 140. Similarly, application interfacemodule 620 may notify a user of mobile device 110 that an application isconsuming resources under a particular billing rate (e.g., per MB fees,pre-paid MB limits, etc.) associated with an access network forfemtocell 140.

Process block 1160 may include the process blocks depicted in FIG. 13.As shown in FIG. 13, process block 1160 may include removing a femtocelluse indicator (block 1310), providing a general notification of datatransfer costs based on the macro cell use (block 1320), providing aper-session notification of data transfer costs based on the macro celluse (block 1330), and/or restricting data transfers using the macro cell(block 1340).

For example, when mobile device 110 moves out of range of femtocell 140,indicator module 610 may receive a new UATI that may not include afemtocell identifier (e.g., indicating the UATI is from a macro basestation). If no femtocell identifier is included in the new UATI,femtocell indicator module 610 may remove the femtocell indicator iconfrom the display. If the user's subscription plan includes distinctionsbetween data transfers using a femtocell (e.g., femtocell 140) versus abase station (e.g., base station 130), application interface module 620may provide a general notification, to the user, of data transfer costsbased on the macro cell connection. Application interface module 620 mayalso notify a user of mobile device 110 that an application is consuming(or attempting to consume) resources of a limited data service (e.g.,per MB fees, pre-paid MB limits, etc.) associated with, for example, anaccess network for macro cell base station 130. Similarly, applicationinterface module 620 may notify a user of mobile device 110 that anapplication is consuming resources under a particular billing rate(e.g., per MB fees, pre-paid MB limits, etc.) associated with an accessnetwork for macro cell base station 130.

FIG. 14 is a flow chart of an example process 1400 for providingfemtocell use identification according to an implementation describedherein. Process 1400 may be performed by femtocell 140. In anotherimplementation, some or all of process 1400 may be performed byfemtocell 140 in conjunction with, for example, mobile device 110 and/oraccount server 160.

Process 1400 may include receiving a user account profile (block 1410)and sending the user account profile to a mobile device (block 1420).For example, account server 160 may receive and store accountinformation associated with mobile devices 110. Account information mayinclude, for example, pricing plan information that differentiatesbetween femtocell usage and macro cell usage. In one implementation,some of the account information may be provided (e.g., via base station130 or femtocell 140) to mobile device 110 to enable mobile device 110to identify differences in pricing for femtocell usage and macro cellusage.

Process 1400 may also include receiving a UATI request (block 1430),obtaining a UATI with a femtocell ID (block 1440), and sending, to themobile device, a UATI with the femtocell ID (block 1450). For example,mobile device 110 may send a UATI request message that may be receivedby a corresponding femtocell 140. Femtocell 140 may, in turn, request aUATI from PCF 125. In response to the UATI request, PCF 125 (e.g., UATIgenerator 410) may assign, to mobile device 110, a unique UATI thatincludes a femtocell identifier. PCF 125 may send the UATI to femtocell140 which may provide the UATI to mobile device 110. In oneimplementation, the femtocell identifier may be a two-bit value commonto all femtocell identifiers within a service provider's network. Thefemtocell identifier may be included within a particular location of theUATI so that mobile device 110 may detect the femtocell identifier and,for example, notify a user that mobile device 110 is connected to afemtocell (e.g., in contrast to a macro cell).

Systems and/or methods described herein may send a request for a uniquewireless network session identifier and may receive, based on therequest, the unique wireless network session identifier. The systemsand/or methods may determine whether the unique wireless network sessionidentifier includes a femtocell identifier. The systems and/or methodsmay apply one set of configuration settings when the unique wirelessnetwork session identifier includes the femtocell identifier, and mayapply a different set of configuration settings when the unique wirelessnetwork session identifier does not include the femtocell identifier.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit theinvention to the precise form disclosed. Modifications and variationsare possible in light of the above teachings or may be acquired frompractice of the invention.

For example, while series of blocks have been described with regard toFIGS. 11-14, the order of the blocks may be modified in otherimplementations. Further, non-dependent blocks may be performed inparallel.

It will be apparent that example aspects, as described above, may beimplemented in many different forms of software, firmware, and hardwarein the implementations illustrated in the figures. The actual softwarecode or specialized control hardware used to implement these aspectsshould not be construed as limiting. Thus, the operation and behavior ofthe aspects were described without reference to the specific softwarecode—it being understood that software and control hardware could bedesigned to implement the aspects based on the description herein.

Further, certain portions of the invention may be implemented as a“component” that performs one or more functions. These components mayinclude hardware, such as a processor, an ASIC, or a FPGA, or acombination of hardware and software.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of the invention. In fact, many ofthese features may be combined in ways not specifically recited in theclaims and/or disclosed in the specification. Although each dependentclaim listed below may directly depend on only one other claim, thedisclosure of the invention includes each dependent claim in combinationwith every other claim in the claim set.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the invention unless explicitlydescribed as such. Also, as used herein, the article “a” is intended toinclude one or more items. Where only one item is intended, the term“one” or similar language is used. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise.

What is claimed is:
 1. A method comprising: receiving, by a mobiledevice, first configuration settings for the mobile device to conductfirst data transfers via a macro cell base station and secondconfiguration settings for the mobile device to conduct second datatransfers via a femtocell, the first configuration settings beingdifferent from the second configuration settings, the firstconfiguration settings including: one or more first settings for firstparticular data transfers, of the first data transfers, initiated by auser, and one or more second settings for second particular datatransfers, of the first data transfers, initiated by an application, theone or more second settings being different from the one or more firstsettings, and the first configuration settings and the secondconfiguration settings varying based on plan information; providing, bythe mobile device, a unicast access terminal identifier (UATI) request;receiving, by the mobile device, a UATI based on the UATI request;determining, by the mobile device, whether the UATI includes a femtocellidentifier that indicates that the mobile device is connected to thefemtocell; and applying, by the mobile device and based on determiningwhether the UATI includes the femtocell identifier, one or more of thefirst configuration settings or one or more of the second configurationsettings.
 2. The method of claim 1, where the UATI request is sent toone of: the macro cell base station, or the femtocell.
 3. The method ofclaim 1, where the UATI includes dedicated femtocell indicator bits. 4.The method of claim 3, where the dedicated femtocell indicator bitsinclude a two-bit pattern associated with a plurality of femtocellswithin a network that includes the femtocell.
 5. The method of claim 1,where applying the second configuration settings for data transfers viathe femtocell includes one or more of: providing, for presentation on adisplay of the mobile device, a femtocell use indicator; providing anotification of a pricing plan associated with data transfers via thefemtocell; or providing a notification of pricing associated with aparticular data transfer session via the femtocell.
 6. The method ofclaim 1, where applying the first configuration settings for datatransfers via the macro cell base station includes one or more of:removing, from a display of the mobile device, a femtocell useindicator; providing a notification of a pricing plan associated withdata transfers via the macro cell base station; providing a notificationof pricing associated with a particular data transfer session via themacro cell base station; or restricting the particular data transfersession via the macro cell base station.
 7. The method of claim 1,further comprising: receiving, from an account server, an accountprofile, associated with the mobile device, that identifies a pricingplan associated with data transfers via the macro cell base station anda pricing plan associated with data transfers via the femtocell, andpresenting information based on the account profile.
 8. The method ofclaim 1, where the macro cell base station and the femtocell are part ofan Evolution-Data Optimized (EVDO) network.
 9. A mobile devicecomprising: a processor, coupled to a memory, to: receive a first set ofconfiguration settings that are to be applied by the mobile device toconduct first data transfers when the mobile device is connected to amacro cell base station and a second set of configuration settings thatare to be applied by the mobile device to conduct second data transferswhen the mobile device is connected to a femtocell, the first set ofconfiguration settings being different from the second set ofconfiguration settings, the first set of configuration settingsincluding: one or more first settings for first particular datatransfers, of the first data transfers, initiated by a user, and one ormore second settings for second particular data transfers, of the firstdata transfers, initiated by an application, the one or more secondsettings being different from the one or more first settings, and thefirst set of configuration settings and the second set of configurationsettings varying based on plan information; send a request for a uniquewireless network session identifier; receive, based on the request, theunique wireless network session identifier; determine whether the uniquewireless network session identifier includes a femtocell identifier thatindicates that the mobile device is connected to the femtocell; andapply, based on determining whether the unique wireless network sessionidentifier includes the femtocell identifier, one or more of the firstset of configuration settings or one or more of the second set ofconfiguration settings.
 10. The mobile device of claim 9, where thefirst set of configuration settings and the second set of configurationsettings are based on input provided by a user of the mobile device. 11.The mobile device of claim 9, where the request for the unique wirelessnetwork session identifier is sent to one of: the macro cell basestation, or the femtocell.
 12. The mobile device of claim 9, where themobile device includes one or more of: a radiotelephone, a personalcommunications system (PCS) terminal, a personal digital assistant(PDA), a wireless device, a smart phone, a laptop computer, or a globalpositioning system (GPS) device.
 13. The mobile device of claim 9, wherethe macro cell base station and the femtocell are part of anEvolution-Data Optimized (EVDO) network.
 14. The mobile device of claim9, where the unique wireless network session identifier includesdedicated femtocell indicator bits.
 15. The mobile device of claim 14,where the dedicated femtocell indicator bits include a two-bit patternassociated with a plurality of femtocells within a network that includesthe femtocell.
 16. The mobile device of claim 9, where the first set ofconfiguration settings includes presenting, on a display of the mobiledevice, a femtocell use indicator that indicates, to a user of themobile device, that the mobile device is connected to a wireless networkvia the femtocell.
 17. A non-transitory computer readable mediumcomprising: one or more instructions which, when executed by a processorof a mobile device, cause the processor to: receive a first set ofconfiguration settings that are to be applied by the mobile device toconduct first data transfers when the mobile device is connected to amacro base station and a second set of configuration settings that areto be applied by the mobile device to conduct second data transfers whenthe mobile device is connected to a femtocell, the first set ofconfiguration settings being different from the second set ofconfiguration settings, the first set of configuration settingsincluding: one or more first settings for first particular datatransfers, of the first data transfers, initiated by a user, and one ormore second settings for second particular data transfers, of the firstdata transfers, initiated by an application, the one or more secondsettings being different from the one or more first settings, and thefirst set of configuration settings and the second set of configurationsettings varying based on plan information; receive a particularidentifier; determine that the particular identifier includes afemtocell identifier that indicates that the mobile device is connectedto the femtocell; and apply, based on determining whether the particularidentifier includes the femtocell identifier, one or more of the firstset of configuration settings or one or more of the second set ofconfiguration settings.
 18. The non-transitory computer readable mediumof claim 17, where the femtocell identifier includes a two-bit patternassociated with a plurality of femtocells that include the femtocell.19. The non-transitory computer readable medium of claim 17, furthercomprising: one or more instructions to: provide, for presentation andafter determining that the particular identifier includes the femtocellidentifier, information regarding pricing changes based on a change fromthe first data transfers via the macro base station to the second datatransfers via the femtocell.
 20. The non-transitory computer readablemedium of claim 17, where the particular identifier is a unicast accessterminal identifier (UATI).